Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4af69e29b633d216c1bbbde04ca23db5e6df13da97830e5ab4c6444f99f1da1

Tx prefix hash: 2d68e34f4974c298182316cdb8bf61c694e5d8a9d8a6cad8f3e370975dba7b5a
Tx public key: efe191485287106ec25c22fb911615f02734b115ebf8f3537e5a1ff0fdb98699
Timestamp: 1750583271 Timestamp [UCT]: 2025-06-22 09:07:51 Age [y:d:h:m:s]: 00:151:12:44:21
Block: 1310345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106170 RingCT/type: yes/0
Extra: 01efe191485287106ec25c22fb911615f02734b115ebf8f3537e5a1ff0fdb98699021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4a51f2b44b4c8d099e64a93de14af016bd31e36f6f3810faf21e34ea865edf8 0.600000000000 1797964 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": 1310355, "vin": [ { "gen": { "height": 1310345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4a51f2b44b4c8d099e64a93de14af016bd31e36f6f3810faf21e34ea865edf8" } } ], "extra": [ 1, 239, 225, 145, 72, 82, 135, 16, 110, 194, 92, 34, 251, 145, 22, 21, 240, 39, 52, 177, 21, 235, 248, 243, 83, 126, 90, 31, 240, 253, 185, 134, 153, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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