Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06e816a950f86817d2d4ffec9c11aebc773c06c1a05b27847ac7ba9a0f197a35

Tx prefix hash: 1b18c1a20a81ee7cae33bd745101d823201630962980b0fdcf6be259688a265b
Tx public key: 795ce135e5a9d1a3c8915e7d439fd6eaf65b73a5de788ceba82fb247c4645551
Timestamp: 1744413854 Timestamp [UCT]: 2025-04-11 23:24:14 Age [y:d:h:m:s]: 00:217:00:44:17
Block: 1259462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152831 RingCT/type: yes/0
Extra: 01795ce135e5a9d1a3c8915e7d439fd6eaf65b73a5de788ceba82fb247c4645551021100000013dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ece117cc2dba7df6aea02a4b28b2590833b4ceb9df60adc7fbaef5b0475eba26 0.600000000000 1746605 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": 1259472, "vin": [ { "gen": { "height": 1259462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ece117cc2dba7df6aea02a4b28b2590833b4ceb9df60adc7fbaef5b0475eba26" } } ], "extra": [ 1, 121, 92, 225, 53, 229, 169, 209, 163, 200, 145, 94, 125, 67, 159, 214, 234, 246, 91, 115, 165, 222, 120, 140, 235, 168, 47, 178, 71, 196, 100, 85, 81, 2, 17, 0, 0, 0, 19, 219, 181, 113, 193, 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