Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 924198c82170d977903242451fb00b4b0f24e493c30cfd303858fa671f71fb1a

Tx prefix hash: f0c678265fb9357d4977a410537da03be10cc53c97aa7852fb5d8773a71fe56a
Tx public key: 22a6e0a79d866e3bda2f1b926375bbfc4d0e24089eb979831af5ac37de1874ca
Timestamp: 1743863915 Timestamp [UCT]: 2025-04-05 14:38:35 Age [y:d:h:m:s]: 00:229:04:19:45
Block: 1254901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161529 RingCT/type: yes/0
Extra: 0122a6e0a79d866e3bda2f1b926375bbfc4d0e24089eb979831af5ac37de1874ca02110000000e6c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9954f2f38ee7343408ced7cc4a2a0cfaae47c73c1caae6b354e519ed1cbcce4 0.600000000000 1741992 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": 1254911, "vin": [ { "gen": { "height": 1254901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9954f2f38ee7343408ced7cc4a2a0cfaae47c73c1caae6b354e519ed1cbcce4" } } ], "extra": [ 1, 34, 166, 224, 167, 157, 134, 110, 59, 218, 47, 27, 146, 99, 117, 187, 252, 77, 14, 36, 8, 158, 185, 121, 131, 26, 245, 172, 55, 222, 24, 116, 202, 2, 17, 0, 0, 0, 14, 108, 152, 170, 61, 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