Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08e12296fed9a7f57e66faa20f761c8f0b1d4c3b7d5d0f5cf87496343812ac9c

Tx prefix hash: de1f7c723bcd8f78d47acda5630931033047f478e646b83d397c54bcea254dfa
Tx public key: 3268073518c530e755968feced02fcd2dc964fc2f7be259e206cb5e5dee87bc3
Timestamp: 1737138597 Timestamp [UCT]: 2025-01-17 18:29:57 Age [y:d:h:m:s]: 00:304:20:25:13
Block: 1199495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215381 RingCT/type: yes/0
Extra: 013268073518c530e755968feced02fcd2dc964fc2f7be259e206cb5e5dee87bc30211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 743e19cd0d71298f6a87c9f570210f5eb13414b625f2f279f78f00dd13a3e1b1 0.600000000000 1686126 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": 1199505, "vin": [ { "gen": { "height": 1199495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "743e19cd0d71298f6a87c9f570210f5eb13414b625f2f279f78f00dd13a3e1b1" } } ], "extra": [ 1, 50, 104, 7, 53, 24, 197, 48, 231, 85, 150, 143, 236, 237, 2, 252, 210, 220, 150, 79, 194, 247, 190, 37, 158, 32, 108, 181, 229, 222, 232, 123, 195, 2, 17, 0, 0, 0, 3, 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