Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60e6b12a5c1f6d22540f9a2f81d0bb1ec54572946b1a624bfb929725b9fd11d6

Tx prefix hash: ef784ddd9f87821dd22f0233c952785c373e9cdaf031777519346817563c3545
Tx public key: 1be4d19f82c8df0d13944fdfd2a56dccb81ee92ad7896e9542fed7bd570d359e
Timestamp: 1735744797 Timestamp [UCT]: 2025-01-01 15:19:57 Age [y:d:h:m:s]: 00:168:04:27:04
Block: 1187961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119896 RingCT/type: yes/0
Extra: 011be4d19f82c8df0d13944fdfd2a56dccb81ee92ad7896e9542fed7bd570d359e02110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c423eb0437d9893ea682165688af9dc87827fa00908a49f26f5fb0f98bdda4fa 0.600000000000 1674460 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": 1187971, "vin": [ { "gen": { "height": 1187961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c423eb0437d9893ea682165688af9dc87827fa00908a49f26f5fb0f98bdda4fa" } } ], "extra": [ 1, 27, 228, 209, 159, 130, 200, 223, 13, 19, 148, 79, 223, 210, 165, 109, 204, 184, 30, 233, 42, 215, 137, 110, 149, 66, 254, 215, 189, 87, 13, 53, 158, 2, 17, 0, 0, 0, 12, 31, 10, 83, 235, 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