Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c361e2b5d5a111aeb95381f2499858456c0aee1273fc6d294c10ad4a799b654

Tx prefix hash: 6b04127f1d626b4d40eb1e76153895781bd3fae240254fbd3cae4d2ed91ae86b
Tx public key: 80b57b66f3b07ed57160c1b8a11b1b8c58da19356b01467cd8e3bf53f25df830
Timestamp: 1720639393 Timestamp [UCT]: 2024-07-10 19:23:13 Age [y:d:h:m:s]: 00:281:22:03:20
Block: 1062859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201431 RingCT/type: yes/0
Extra: 0180b57b66f3b07ed57160c1b8a11b1b8c58da19356b01467cd8e3bf53f25df83002110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5686e453a74b8e8e60ed55bf9063686f1f34915f2caa70f10ab96bea7afc9580 0.600000000000 1533370 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": 1062869, "vin": [ { "gen": { "height": 1062859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5686e453a74b8e8e60ed55bf9063686f1f34915f2caa70f10ab96bea7afc9580" } } ], "extra": [ 1, 128, 181, 123, 102, 243, 176, 126, 213, 113, 96, 193, 184, 161, 27, 27, 140, 88, 218, 25, 53, 107, 1, 70, 124, 216, 227, 191, 83, 242, 93, 248, 48, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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