Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5839ffe18581e89efb111cb09005d0fd36444f2594c0e4d12fa6f4571918a0a1

Tx prefix hash: d599a6f9c1fe8d32ed72e7d438c6cd08cf04cf11fb6b0f4492c7bfff83fa8430
Tx public key: 7040a35891102504e6c1da2ef02d30f331e61cb69bff60706ee9200a3b9046c8
Timestamp: 1737668663 Timestamp [UCT]: 2025-01-23 21:44:23 Age [y:d:h:m:s]: 00:147:07:05:30
Block: 1203839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104998 RingCT/type: yes/0
Extra: 017040a35891102504e6c1da2ef02d30f331e61cb69bff60706ee9200a3b9046c80211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd81aa40b72f169c2b6e6c3272ae1ce306672c266cd33e76e55d48be3a1b4317 0.600000000000 1690518 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": 1203849, "vin": [ { "gen": { "height": 1203839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd81aa40b72f169c2b6e6c3272ae1ce306672c266cd33e76e55d48be3a1b4317" } } ], "extra": [ 1, 112, 64, 163, 88, 145, 16, 37, 4, 230, 193, 218, 46, 240, 45, 48, 243, 49, 230, 28, 182, 155, 255, 96, 112, 110, 233, 32, 10, 59, 144, 70, 200, 2, 17, 0, 0, 0, 1, 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