Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5734450da671e66e6d353989e85363df284a6863d11c745eccfe59ec9af223ef

Tx prefix hash: 347e16869c9d8a1c51250dd284c3953c436da238408037bc783706b5e7088194
Tx public key: dec7b759fb978ee5820ab7e249eecf3eb26a5a0bde1fc2dca5e4f14f4a9f34c7
Timestamp: 1725209231 Timestamp [UCT]: 2024-09-01 16:47:11 Age [y:d:h:m:s]: 00:228:17:27:08
Block: 1100737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163337 RingCT/type: yes/0
Extra: 01dec7b759fb978ee5820ab7e249eecf3eb26a5a0bde1fc2dca5e4f14f4a9f34c7021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d810863509875e863407be953c009dcec66ba09abbb0c76c55361205ac99f2c2 0.600000000000 1576718 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": 1100747, "vin": [ { "gen": { "height": 1100737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d810863509875e863407be953c009dcec66ba09abbb0c76c55361205ac99f2c2" } } ], "extra": [ 1, 222, 199, 183, 89, 251, 151, 142, 229, 130, 10, 183, 226, 73, 238, 207, 62, 178, 106, 90, 11, 222, 31, 194, 220, 165, 228, 241, 79, 74, 159, 52, 199, 2, 17, 0, 0, 0, 9, 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