Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e53942662c102312d4b44c7c874b23d056e1574a79b7ff981859866fd32d165e

Tx prefix hash: 74621b3f46e0377746bd18c4baafcbb1d95e3e0866c3df3f9b7c8881a0e0a35e
Tx public key: 1c522df3b5f14744ad265eceb8bfd920ef2d2717b58949d59d52579e8cc704f2
Timestamp: 1748095156 Timestamp [UCT]: 2025-05-24 13:59:16 Age [y:d:h:m:s]: 00:179:00:13:18
Block: 1289946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125625 RingCT/type: yes/0
Extra: 011c522df3b5f14744ad265eceb8bfd920ef2d2717b58949d59d52579e8cc704f20211000000051f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa66fdf5ea72e40cd1662a1b4305d26dafd937da5c962570b0432407f7951f17 0.600000000000 1777415 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": 1289956, "vin": [ { "gen": { "height": 1289946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa66fdf5ea72e40cd1662a1b4305d26dafd937da5c962570b0432407f7951f17" } } ], "extra": [ 1, 28, 82, 45, 243, 181, 241, 71, 68, 173, 38, 94, 206, 184, 191, 217, 32, 239, 45, 39, 23, 181, 137, 73, 213, 157, 82, 87, 158, 140, 199, 4, 242, 2, 17, 0, 0, 0, 5, 31, 144, 81, 122, 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