Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f6d34128e8d03a247711ed770f533a4fdcfd8a75933847090e5af6df92fc29b

Tx prefix hash: 5eb1c1134b0a8ada83496106c0c4d9450df9b4727d665f5b1530eb976e4e6993
Tx public key: 0796335c949aa5de0dee664a710773ab28cc86aab11b741fe9b96c4b9533fad7
Timestamp: 1733089697 Timestamp [UCT]: 2024-12-01 21:48:17 Age [y:d:h:m:s]: 00:112:16:48:59
Block: 1165980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80340 RingCT/type: yes/0
Extra: 010796335c949aa5de0dee664a710773ab28cc86aab11b741fe9b96c4b9533fad702110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c9f28e81ef1b361c56e20c493e86c0e29ce28a329319885d07a9e1786dad1cb 0.600000000000 1651657 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": 1165990, "vin": [ { "gen": { "height": 1165980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c9f28e81ef1b361c56e20c493e86c0e29ce28a329319885d07a9e1786dad1cb" } } ], "extra": [ 1, 7, 150, 51, 92, 148, 154, 165, 222, 13, 238, 102, 74, 113, 7, 115, 171, 40, 204, 134, 170, 177, 27, 116, 31, 233, 185, 108, 75, 149, 51, 250, 215, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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