Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a32d9728b323c3cdb959662eaebb9d3f15533f4a5eb5443f88956eb9cdc0093a

Tx prefix hash: c9dd1e31eed3bb3638afff92d58f440e2b2526b03e6b821583973af3f00c9c5a
Tx public key: eb2b5add7867c205278e1eeac1a3143f2ac74f83547dc1a3442b3de4e3b56848
Timestamp: 1745854713 Timestamp [UCT]: 2025-04-28 15:38:33 Age [y:d:h:m:s]: 00:038:12:43:25
Block: 1271397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27553 RingCT/type: yes/0
Extra: 01eb2b5add7867c205278e1eeac1a3143f2ac74f83547dc1a3442b3de4e3b568480211000000079f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64e25c8f490dd954e42e276ddb54c36433d03ccc6cd129417c82a9c0c926956c 0.600000000000 1758658 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": 1271407, "vin": [ { "gen": { "height": 1271397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64e25c8f490dd954e42e276ddb54c36433d03ccc6cd129417c82a9c0c926956c" } } ], "extra": [ 1, 235, 43, 90, 221, 120, 103, 194, 5, 39, 142, 30, 234, 193, 163, 20, 63, 42, 199, 79, 131, 84, 125, 193, 163, 68, 43, 61, 228, 227, 181, 104, 72, 2, 17, 0, 0, 0, 7, 159, 159, 230, 140, 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