Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ab7cd79f340358ae49c01a04ccd17255ea609df7bf5041b08d25cb38ec647f2

Tx prefix hash: 8a00ba4d6f13d704731ca658d8908e9f451a917d9d59eb81e59eac9e6fef637b
Tx public key: a0ce44cb27e1f3ab0970a8c165cb0c05e320b0424d3ee204279eb55d15ad701f
Timestamp: 1731166859 Timestamp [UCT]: 2024-11-09 15:40:59 Age [y:d:h:m:s]: 00:132:08:40:41
Block: 1150055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94410 RingCT/type: yes/0
Extra: 01a0ce44cb27e1f3ab0970a8c165cb0c05e320b0424d3ee204279eb55d15ad701f021100000003a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a29ba0256cb01d2291cb4dd924dd0fc739fb630952f9d836775b427b2e0df762 0.600000000000 1635256 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": 1150065, "vin": [ { "gen": { "height": 1150055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a29ba0256cb01d2291cb4dd924dd0fc739fb630952f9d836775b427b2e0df762" } } ], "extra": [ 1, 160, 206, 68, 203, 39, 225, 243, 171, 9, 112, 168, 193, 101, 203, 12, 5, 227, 32, 176, 66, 77, 62, 226, 4, 39, 158, 181, 93, 21, 173, 112, 31, 2, 17, 0, 0, 0, 3, 161, 29, 186, 152, 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