Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a89fa86011bb995bcb06e49bdd8533260ff5a17eb37375e5deafa969b6a7db1c

Tx prefix hash: 1c865066f0d43be2b4ba5f66c7b8afdd37d268b8f2d969f0d14abbffb5637812
Tx public key: e0de9d60834f83d8dd547fe6ea4c2aa920dedb94a8acba01b63ab5e753d873b8
Timestamp: 1723912106 Timestamp [UCT]: 2024-08-17 16:28:26 Age [y:d:h:m:s]: 00:280:00:46:21
Block: 1089992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200048 RingCT/type: yes/0
Extra: 01e0de9d60834f83d8dd547fe6ea4c2aa920dedb94a8acba01b63ab5e753d873b8021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43660e4a798173a6f617f65ce704c8f8c1e950dedfee11417bf7fc5418a74762 0.600000000000 1564615 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": 1090002, "vin": [ { "gen": { "height": 1089992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43660e4a798173a6f617f65ce704c8f8c1e950dedfee11417bf7fc5418a74762" } } ], "extra": [ 1, 224, 222, 157, 96, 131, 79, 131, 216, 221, 84, 127, 230, 234, 76, 42, 169, 32, 222, 219, 148, 168, 172, 186, 1, 182, 58, 181, 231, 83, 216, 115, 184, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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