Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee04c4305902fb51e734b897c440cedc155719c42bce3a4fd9ac2357aae66d4b

Tx prefix hash: d9525a7d732351f4ff0d581b0388da7678123b1644e5ff48a5576de2b1e42658
Tx public key: ff2b88c0aa37f929114434e3aa2a6828b3fa41751ea128234476e341c486a9e5
Timestamp: 1740024919 Timestamp [UCT]: 2025-02-20 04:15:19 Age [y:d:h:m:s]: 00:264:20:23:04
Block: 1223101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187063 RingCT/type: yes/0
Extra: 01ff2b88c0aa37f929114434e3aa2a6828b3fa41751ea128234476e341c486a9e50211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f372ab85fbb9458c276cb8162f12ee1971e26862a7b965bcdd5acbb2b3d634e 0.600000000000 1709956 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": 1223111, "vin": [ { "gen": { "height": 1223101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f372ab85fbb9458c276cb8162f12ee1971e26862a7b965bcdd5acbb2b3d634e" } } ], "extra": [ 1, 255, 43, 136, 192, 170, 55, 249, 41, 17, 68, 52, 227, 170, 42, 104, 40, 179, 250, 65, 117, 30, 161, 40, 35, 68, 118, 227, 65, 196, 134, 169, 229, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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