Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84845ae709b4895b69303892ad99801b2f61feee938ed14995396d4e4f5a188e

Tx prefix hash: b530f7c0897063dae13f1f8bab35a8c9bb72869b998fa1f323392f3a5d01be52
Tx public key: f715bfd03879028ed1625f4e815ccbec8f66d584b9601bb7ff8c3e71166eab1b
Timestamp: 1718382784 Timestamp [UCT]: 2024-06-14 16:33:04 Age [y:d:h:m:s]: 01:148:20:23:08
Block: 1044149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364942 RingCT/type: yes/0
Extra: 01f715bfd03879028ed1625f4e815ccbec8f66d584b9601bb7ff8c3e71166eab1b0211000000028fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c15f9791cf42637bb2e73412d14a44f9d9f267b2d19f3be7154e445b353228a8 0.600000000000 1513380 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": 1044159, "vin": [ { "gen": { "height": 1044149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c15f9791cf42637bb2e73412d14a44f9d9f267b2d19f3be7154e445b353228a8" } } ], "extra": [ 1, 247, 21, 191, 208, 56, 121, 2, 142, 209, 98, 95, 78, 129, 92, 203, 236, 143, 102, 213, 132, 185, 96, 27, 183, 255, 140, 62, 113, 22, 110, 171, 27, 2, 17, 0, 0, 0, 2, 143, 218, 155, 45, 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