Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 150a4ef9102259e0b22669929cd05a61d787814b452890dc6c523266d308a6ea

Tx prefix hash: c02ad66ea1a1d5e8b57d0878fc35660d172bebf06b04b581dbaebd1de4b3516b
Tx public key: c492daa10e0f3cf085cb770453c322157e0b2a2d0ea11c43bbae2af90ca0d652
Timestamp: 1734587212 Timestamp [UCT]: 2024-12-19 05:46:52 Age [y:d:h:m:s]: 00:096:05:48:58
Block: 1178398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68544 RingCT/type: yes/0
Extra: 01c492daa10e0f3cf085cb770453c322157e0b2a2d0ea11c43bbae2af90ca0d652021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2280d5de42a12b70c240a2e776576e136d1668a9c1aa9fa870a80d1671344769 0.600000000000 1664785 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": 1178408, "vin": [ { "gen": { "height": 1178398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2280d5de42a12b70c240a2e776576e136d1668a9c1aa9fa870a80d1671344769" } } ], "extra": [ 1, 196, 146, 218, 161, 14, 15, 60, 240, 133, 203, 119, 4, 83, 195, 34, 21, 126, 11, 42, 45, 14, 161, 28, 67, 187, 174, 42, 249, 12, 160, 214, 82, 2, 17, 0, 0, 0, 3, 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