Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8be5128ab236eac5d5a7139e1aa0778c3a88348d2c4043afeb8bc682916ec9f

Tx prefix hash: 915fc208c599512863e1345c345bd4dc1e82231a6d6d1fab07de09484aeb9bf0
Tx public key: 1fd8ce081e49f6675e30a9fd217bfe0b7e7ac78f874c7564e697f78611257aab
Timestamp: 1703425866 Timestamp [UCT]: 2023-12-24 13:51:06 Age [y:d:h:m:s]: 01:168:07:30:12
Block: 920150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381462 RingCT/type: yes/0
Extra: 011fd8ce081e49f6675e30a9fd217bfe0b7e7ac78f874c7564e697f78611257aab021100000004ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cff2c80206485ec7800a32dd9b6d83b987855ed5795107e290b871e46c7ca963 0.600000000000 1377828 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": 920160, "vin": [ { "gen": { "height": 920150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cff2c80206485ec7800a32dd9b6d83b987855ed5795107e290b871e46c7ca963" } } ], "extra": [ 1, 31, 216, 206, 8, 30, 73, 246, 103, 94, 48, 169, 253, 33, 123, 254, 11, 126, 122, 199, 143, 135, 76, 117, 100, 230, 151, 247, 134, 17, 37, 122, 171, 2, 17, 0, 0, 0, 4, 173, 86, 148, 172, 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