Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5237928007c2aff37bc554d87a6cb82477184a228a1e6074a57c4d3d0329028c

Tx prefix hash: 456e80d5ab47e7964a4e6b9ebd285e7e8f9d77cdd458701c00f68920b35472e2
Tx public key: 413f52a356f10c95b57b43d6e29304a59ffe6be8eddfbee24f6b831ae0d7311b
Timestamp: 1755316730 Timestamp [UCT]: 2025-08-16 03:58:50 Age [y:d:h:m:s]: 00:109:22:48:41
Block: 1347616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78356 RingCT/type: yes/0
Extra: 01413f52a356f10c95b57b43d6e29304a59ffe6be8eddfbee24f6b831ae0d7311b02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49314f5d4e706c2beaf220154d49f031be39f817cf442dccb17fe98711166ef8 0.600000000000 1835535 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": 1347626, "vin": [ { "gen": { "height": 1347616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49314f5d4e706c2beaf220154d49f031be39f817cf442dccb17fe98711166ef8" } } ], "extra": [ 1, 65, 63, 82, 163, 86, 241, 12, 149, 181, 123, 67, 214, 226, 147, 4, 165, 159, 254, 107, 232, 237, 223, 190, 226, 79, 107, 131, 26, 224, 215, 49, 27, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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