Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee81d375c5d1c611f5a98eadcff68c057fb663b7fd97e05e26029132d5e1eb71

Tx prefix hash: f68337daed0bc60d739579e75c18c0c798b168fd3fe111219d6eea15bc4b0fcc
Tx public key: 2d4a18de79a3e33cb54ec54eb1c5658aa3bf5e81de4cad32af8fac55feee873b
Timestamp: 1751185129 Timestamp [UCT]: 2025-06-29 08:18:49 Age [y:d:h:m:s]: 00:145:07:36:49
Block: 1315080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101963 RingCT/type: yes/0
Extra: 012d4a18de79a3e33cb54ec54eb1c5658aa3bf5e81de4cad32af8fac55feee873b02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cac680d943ca54182f3c07ff99b3ccc2f95a333e11a76ab02167c947f9616ca 0.600000000000 1802733 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": 1315090, "vin": [ { "gen": { "height": 1315080 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cac680d943ca54182f3c07ff99b3ccc2f95a333e11a76ab02167c947f9616ca" } } ], "extra": [ 1, 45, 74, 24, 222, 121, 163, 227, 60, 181, 78, 197, 78, 177, 197, 101, 138, 163, 191, 94, 129, 222, 76, 173, 50, 175, 143, 172, 85, 254, 238, 135, 59, 2, 17, 0, 0, 0, 2, 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