Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71b1c0f47d2c0d47cd83842fd9ecf02d67b078b18401bfa3ecee6a4c445c3a78

Tx prefix hash: 9d8fec0180851a1191c234654368c6fe20d0d25190b01a87c48320fee0b19561
Tx public key: 1a185a321037a83dfb81037618d5ef541ffde460ace07c2ce7808da869e3ec08
Timestamp: 1737537437 Timestamp [UCT]: 2025-01-22 09:17:17 Age [y:d:h:m:s]: 00:149:16:10:12
Block: 1202753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106671 RingCT/type: yes/0
Extra: 011a185a321037a83dfb81037618d5ef541ffde460ace07c2ce7808da869e3ec0802110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3a34612ab3cd7e45603e043a9d7d4165a8ca02cb49e85c41f1aeee8a6fe71d3 0.600000000000 1689418 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": 1202763, "vin": [ { "gen": { "height": 1202753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3a34612ab3cd7e45603e043a9d7d4165a8ca02cb49e85c41f1aeee8a6fe71d3" } } ], "extra": [ 1, 26, 24, 90, 50, 16, 55, 168, 61, 251, 129, 3, 118, 24, 213, 239, 84, 31, 253, 228, 96, 172, 224, 124, 44, 231, 128, 141, 168, 105, 227, 236, 8, 2, 17, 0, 0, 0, 11, 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