Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09444f0d722bada101168ad6b20a0dcb1d0a18face31bfcd0ff6eca411468699

Tx prefix hash: b489091de07bac488bfcc9c1a3397eb6cfa2fc7830f0e527b90d9f41353dee2e
Tx public key: 1e4cf9b09bb66fb814cf99ff35b67a72b23cd37addc73f40e29f35caa4057f0a
Timestamp: 1643561706 Timestamp [UCT]: 2022-01-30 16:55:06 Age [y:d:h:m:s]: 03:009:05:31:09
Block: 428606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 785765 RingCT/type: yes/0
Extra: 011e4cf9b09bb66fb814cf99ff35b67a72b23cd37addc73f40e29f35caa4057f0a0211000000064a0f5013000000000000000000

1 output(s) for total of 23.328500633000 dcy

stealth address amount amount idx
00: baada1c43b9031f093eb5ebc50c8b8912b79a7f6db214268a93d87862f0e34b9 23.328500633000 838044 of 0

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": 428616, "vin": [ { "gen": { "height": 428606 } } ], "vout": [ { "amount": 23328500633, "target": { "key": "baada1c43b9031f093eb5ebc50c8b8912b79a7f6db214268a93d87862f0e34b9" } } ], "extra": [ 1, 30, 76, 249, 176, 155, 182, 111, 184, 20, 207, 153, 255, 53, 182, 122, 114, 178, 60, 211, 122, 221, 199, 63, 64, 226, 159, 53, 202, 164, 5, 127, 10, 2, 17, 0, 0, 0, 6, 74, 15, 80, 19, 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