Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac3ec322ac0089c63e83d1adeaa7bb4cd5edb4336bf9928f50c623556cc8f76a

Tx prefix hash: 6db31170754cb27d8205e60daa87bb108ec4a49d6a261752a0e066a3b28abd66
Tx public key: 5fe26a033fbca75976f8f03ead1017b18e28f923c8fefc8ceed5895bfc83cefc
Timestamp: 1760506070 Timestamp [UCT]: 2025-10-15 05:27:50 Age [y:d:h:m:s]: 00:026:12:26:40
Block: 1390265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18971 RingCT/type: yes/0
Extra: 015fe26a033fbca75976f8f03ead1017b18e28f923c8fefc8ceed5895bfc83cefc0211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49d2254ae0fa0f2055e16b0dbd744e29d1d0455f2dacf06c840e0558b8450b8f 0.600000000000 1878502 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": 1390275, "vin": [ { "gen": { "height": 1390265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49d2254ae0fa0f2055e16b0dbd744e29d1d0455f2dacf06c840e0558b8450b8f" } } ], "extra": [ 1, 95, 226, 106, 3, 63, 188, 167, 89, 118, 248, 240, 62, 173, 16, 23, 177, 142, 40, 249, 35, 200, 254, 252, 140, 238, 213, 137, 91, 252, 131, 206, 252, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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