Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 206ddac6c753171cdbf1e97b6556b9ddfbddeef78fd55cc3726ab59627be9bba

Tx prefix hash: e99e7192842cd507f4c85200a43feaaa88b3369fd16a66cef0dcf9f8b37a5d8e
Tx public key: c71c3da7a511e16010a2e58e24e51344c1bcb6d5d8fbd6b01d148cb0744f84ef
Timestamp: 1731535699 Timestamp [UCT]: 2024-11-13 22:08:19 Age [y:d:h:m:s]: 00:141:03:45:47
Block: 1153103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100694 RingCT/type: yes/0
Extra: 01c71c3da7a511e16010a2e58e24e51344c1bcb6d5d8fbd6b01d148cb0744f84ef021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a999fdfa5b3a417df1961493dbd2bef8556197882cb64668cc135e6981b1c8db 0.600000000000 1638710 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": 1153113, "vin": [ { "gen": { "height": 1153103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a999fdfa5b3a417df1961493dbd2bef8556197882cb64668cc135e6981b1c8db" } } ], "extra": [ 1, 199, 28, 61, 167, 165, 17, 225, 96, 16, 162, 229, 142, 36, 229, 19, 68, 193, 188, 182, 213, 216, 251, 214, 176, 29, 20, 140, 176, 116, 79, 132, 239, 2, 17, 0, 0, 0, 1, 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