Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 124d1f26c6a0a293e07797aba59d2b19af31cca1c72195e7d959bf296e8cb85e

Tx prefix hash: 893218180aa0240b46efa00cb092f0c5fd05dcee277093efe1170aa9c33132a5
Tx public key: a810dc1372b08a929e911d1118f68e14813bd7b4eca8be7d7add29f957cede58
Timestamp: 1706331831 Timestamp [UCT]: 2024-01-27 05:03:51 Age [y:d:h:m:s]: 01:066:05:28:15
Block: 944210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308424 RingCT/type: yes/0
Extra: 01a810dc1372b08a929e911d1118f68e14813bd7b4eca8be7d7add29f957cede580211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9770d501658bb3bbe96b5c9488c312dd8465014ed90e4556ae9e805eb4ece7a 0.600000000000 1402446 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": 944220, "vin": [ { "gen": { "height": 944210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9770d501658bb3bbe96b5c9488c312dd8465014ed90e4556ae9e805eb4ece7a" } } ], "extra": [ 1, 168, 16, 220, 19, 114, 176, 138, 146, 158, 145, 29, 17, 24, 246, 142, 20, 129, 59, 215, 180, 236, 168, 190, 125, 122, 221, 41, 249, 87, 206, 222, 88, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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