Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: ba6b8c2b21d544c9f545491b82233d84813a1a73895b8dc4cccf6890d2500418

Tx prefix hash: 3b05ece00183de1a0596f9313271c514c8e0fa5261b4d02dc75f40c870d247d7
Tx public key: 10fba8e7cae9ed797bd0ce3810c91308b61067fea516b8f0a314bd48b4c0c8e6
Timestamp: 1714351299 Timestamp [UCT]: 2024-04-29 00:41:39 Age [y:d:h:m:s]: 01:048:21:18:32
Block: 1010721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295799 RingCT/type: yes/0
Extra: 0110fba8e7cae9ed797bd0ce3810c91308b61067fea516b8f0a314bd48b4c0c8e602110000000d52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b0a17ce1a4ad491d14b857e4e429f37b218f1ae4cb0a55aad9983a66af5315b 0.600000000000 1472757 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1010731, "vin": [ { "gen": { "height": 1010721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b0a17ce1a4ad491d14b857e4e429f37b218f1ae4cb0a55aad9983a66af5315b" } } ], "extra": [ 1, 16, 251, 168, 231, 202, 233, 237, 121, 123, 208, 206, 56, 16, 201, 19, 8, 182, 16, 103, 254, 165, 22, 184, 240, 163, 20, 189, 72, 180, 192, 200, 230, 2, 17, 0, 0, 0, 13, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8