Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e226af8c003f6d9009638d1641d5b73a0083798a4512c1a95fb190c62f13d27

Tx prefix hash: dd964651b9f7ffbe1579f7bc0fec7c4073bf1908ca3510cc59e499978fc421e1
Tx public key: 19ccacf0e9d18a41d93169b001f7c3b6a39c7faf4a4e7a81d946b06e31669a53
Timestamp: 1702422846 Timestamp [UCT]: 2023-12-12 23:14:06 Age [y:d:h:m:s]: 01:110:01:47:33
Block: 911851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339781 RingCT/type: yes/0
Extra: 0119ccacf0e9d18a41d93169b001f7c3b6a39c7faf4a4e7a81d946b06e31669a53021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec1a2569678ebcbf033c66852a1612eb58fbd46483e68e9678dfbe3419515033 0.600000000000 1369067 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": 911861, "vin": [ { "gen": { "height": 911851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec1a2569678ebcbf033c66852a1612eb58fbd46483e68e9678dfbe3419515033" } } ], "extra": [ 1, 25, 204, 172, 240, 233, 209, 138, 65, 217, 49, 105, 176, 1, 247, 195, 182, 163, 156, 127, 175, 74, 78, 122, 129, 217, 70, 176, 110, 49, 102, 154, 83, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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