Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7d2d419f14ea65830db9015f9dc622afeaa36f446ae6e2707fec3d2cce25bee

Tx prefix hash: 83a3bb4117f4cd92cdb3aa6ce3dbcdb87e5a24054aadd97df48b1010f1774aa5
Tx public key: d255333d6a54f70428001415fb9b025e289032c7b151ebd7c077b56159f97975
Timestamp: 1743232599 Timestamp [UCT]: 2025-03-29 07:16:39 Age [y:d:h:m:s]: 00:286:15:44:20
Block: 1249675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202697 RingCT/type: yes/0
Extra: 01d255333d6a54f70428001415fb9b025e289032c7b151ebd7c077b56159f979750211000000071a970403000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb2bab4f1fe1820cf6511b7e9c90e2d8c16d6edcbcf3685f8e5765b225800688 0.600000000000 1736716 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": 1249685, "vin": [ { "gen": { "height": 1249675 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb2bab4f1fe1820cf6511b7e9c90e2d8c16d6edcbcf3685f8e5765b225800688" } } ], "extra": [ 1, 210, 85, 51, 61, 106, 84, 247, 4, 40, 0, 20, 21, 251, 155, 2, 94, 40, 144, 50, 199, 177, 81, 235, 215, 192, 119, 181, 97, 89, 249, 121, 117, 2, 17, 0, 0, 0, 7, 26, 151, 4, 3, 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