Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e37bf7d62cf5c4b1115da79e55fd551ab9372ed5850ce86dc037dadbae8ea403

Tx prefix hash: ab8f31ec36ad158c2074a7e7c7d625b326e3dfb226f814f536b9b9bab1c9deba
Tx public key: e16a8ac97ff8f3912338eff3e0dfc3c8a89bc3817f169bae514a6fe56ef48bfc
Timestamp: 1744125091 Timestamp [UCT]: 2025-04-08 15:11:31 Age [y:d:h:m:s]: 00:294:15:10:21
Block: 1257064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208216 RingCT/type: yes/0
Extra: 01e16a8ac97ff8f3912338eff3e0dfc3c8a89bc3817f169bae514a6fe56ef48bfc0211000000036c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 445408f8ee585bf76d5e65ad07d0c17c683c991d3439822802139ecb4ec272dc 0.600000000000 1744183 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": 1257074, "vin": [ { "gen": { "height": 1257064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "445408f8ee585bf76d5e65ad07d0c17c683c991d3439822802139ecb4ec272dc" } } ], "extra": [ 1, 225, 106, 138, 201, 127, 248, 243, 145, 35, 56, 239, 243, 224, 223, 195, 200, 168, 155, 195, 129, 127, 22, 155, 174, 81, 74, 111, 229, 110, 244, 139, 252, 2, 17, 0, 0, 0, 3, 108, 152, 170, 61, 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