Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb0be445be8355b25042f5c103f12be9da5b29ef732eb3b5a7a6e0393f09844f

Tx prefix hash: 3b93d379f5556fe5391f3738b743063e9b3d72341298ac321f293a476e716c1a
Tx public key: bc266e71f5b9ce7f371b0fb3f02b132aaa84781e6e8d173381cc3df97ee116b9
Timestamp: 1717725114 Timestamp [UCT]: 2024-06-07 01:51:54 Age [y:d:h:m:s]: 01:167:22:39:40
Block: 1038696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378611 RingCT/type: yes/0
Extra: 01bc266e71f5b9ce7f371b0fb3f02b132aaa84781e6e8d173381cc3df97ee116b902110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c21ad87ecbf271baaf7b996a205ed1bfaaf2da27a119c314cd59ce290df1b01b 0.600000000000 1507257 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": 1038706, "vin": [ { "gen": { "height": 1038696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c21ad87ecbf271baaf7b996a205ed1bfaaf2da27a119c314cd59ce290df1b01b" } } ], "extra": [ 1, 188, 38, 110, 113, 245, 185, 206, 127, 55, 27, 15, 179, 240, 43, 19, 42, 170, 132, 120, 30, 110, 141, 23, 51, 129, 204, 61, 249, 126, 225, 22, 185, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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