Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8454c0cdb4843a9e1fc5ee9f4563c4e88d690dbe5e027e1bc41522d1fe0e7cf1

Tx prefix hash: e5d3b57b6ea72e957d5d51aefb97aecb1433e05ec750486a6778860901645ddb
Tx public key: 546155fc866190b8c3de1b85384b9ab1b98522eb4a6a27ac16d73fc37f2294ce
Timestamp: 1581666030 Timestamp [UCT]: 2020-02-14 07:40:30 Age [y:d:h:m:s]: 05:028:23:28:06
Block: 64681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1173567 RingCT/type: yes/0
Extra: 01546155fc866190b8c3de1b85384b9ab1b98522eb4a6a27ac16d73fc37f2294ce0211000000217adf42d3000000000000000000

1 output(s) for total of 374.701824797000 dcy

stealth address amount amount idx
00: 0cc2f6e07a29d83271e190fceb788160fa9a489bb13d0b0b71829620c65da070 374.701824797000 119333 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": 64691, "vin": [ { "gen": { "height": 64681 } } ], "vout": [ { "amount": 374701824797, "target": { "key": "0cc2f6e07a29d83271e190fceb788160fa9a489bb13d0b0b71829620c65da070" } } ], "extra": [ 1, 84, 97, 85, 252, 134, 97, 144, 184, 195, 222, 27, 133, 56, 75, 154, 177, 185, 133, 34, 235, 74, 106, 39, 172, 22, 215, 63, 195, 127, 34, 148, 206, 2, 17, 0, 0, 0, 33, 122, 223, 66, 211, 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