Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a384039f10937dfb946b34e5739e5f3c0aff2c462d21c44cb248d4dbcab84f3

Tx prefix hash: 5319abb6717754309fd150289547cef71fdfaf74ce8f509315cf1af8fa648908
Tx public key: b16c1c6f28da647b523e1219fd783abb57c04b4bcd3c175c5087a56a2760da13
Timestamp: 1719632914 Timestamp [UCT]: 2024-06-29 03:48:34 Age [y:d:h:m:s]: 00:283:07:14:42
Block: 1054511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202417 RingCT/type: yes/0
Extra: 01b16c1c6f28da647b523e1219fd783abb57c04b4bcd3c175c5087a56a2760da130211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a4447e37d67a9383f317e8cd9b886fd1d1e10c6d50f7d683a1de207db19a505 0.600000000000 1524874 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": 1054521, "vin": [ { "gen": { "height": 1054511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a4447e37d67a9383f317e8cd9b886fd1d1e10c6d50f7d683a1de207db19a505" } } ], "extra": [ 1, 177, 108, 28, 111, 40, 218, 100, 123, 82, 62, 18, 25, 253, 120, 58, 187, 87, 192, 75, 75, 205, 60, 23, 92, 80, 135, 165, 106, 39, 96, 218, 19, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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