Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45e2ad4e79f5c99de0db5f6da9481709f6260cb857a312529de23f8a9546b436

Tx prefix hash: b6887141df9e7897249cabc8fb341939cd4247a06363aca5e95c6172a907f19e
Tx public key: 336352fe96d89154f907a73cc81afe2037a1bff1422e8f83049ce1bd1b0ac91c
Timestamp: 1734990712 Timestamp [UCT]: 2024-12-23 21:51:52 Age [y:d:h:m:s]: 00:090:04:40:37
Block: 1181725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64227 RingCT/type: yes/0
Extra: 01336352fe96d89154f907a73cc81afe2037a1bff1422e8f83049ce1bd1b0ac91c0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7043a8d7d5ad31b50ec8bd166977aa6173d28d319f8d770df242e237ea65e4b5 0.600000000000 1668150 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": 1181735, "vin": [ { "gen": { "height": 1181725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7043a8d7d5ad31b50ec8bd166977aa6173d28d319f8d770df242e237ea65e4b5" } } ], "extra": [ 1, 51, 99, 82, 254, 150, 216, 145, 84, 249, 7, 167, 60, 200, 26, 254, 32, 55, 161, 191, 241, 66, 46, 143, 131, 4, 156, 225, 189, 27, 10, 201, 28, 2, 17, 0, 0, 0, 2, 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