Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87038ab8a4602db849e6a8d733ec36e5e5bd226a690d0ae21290810129beeb03

Tx prefix hash: 5a8eeb2082e12c048c4b17f6471d3157e558296d5a748c9833643834eeb4aeb3
Tx public key: aeeafccec4ec3c7295ef24f54af3930d310a1f522ec7a0a3a97791c71455a61b
Timestamp: 1755337744 Timestamp [UCT]: 2025-08-16 09:49:04 Age [y:d:h:m:s]: 00:096:08:07:46
Block: 1347766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68634 RingCT/type: yes/0
Extra: 01aeeafccec4ec3c7295ef24f54af3930d310a1f522ec7a0a3a97791c71455a61b0211000000048368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e00ecc02342619da351dbf7c7aa4f5b04e8bc0fc4a8d9cdfc6efe86115df108 0.600000000000 1835687 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": 1347776, "vin": [ { "gen": { "height": 1347766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e00ecc02342619da351dbf7c7aa4f5b04e8bc0fc4a8d9cdfc6efe86115df108" } } ], "extra": [ 1, 174, 234, 252, 206, 196, 236, 60, 114, 149, 239, 36, 245, 74, 243, 147, 13, 49, 10, 31, 82, 46, 199, 160, 163, 169, 119, 145, 199, 20, 85, 166, 27, 2, 17, 0, 0, 0, 4, 131, 104, 38, 109, 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