Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ceacefc63670948275227e7b38ef6669e5dfaf695a6cdb289da6632dfeb64c5

Tx prefix hash: 071cf0885e06fd43ab72b4f1fec527ad4c7c7a2b7344f3b9cfb8674f6bdf1bc8
Tx public key: bc6a0d284c45336fe1e3b451a2476cdd9b7cfd6865de4deb4f22fbafd00dc7a5
Timestamp: 1625405671 Timestamp [UCT]: 2021-07-04 13:34:31 Age [y:d:h:m:s]: 03:233:18:40:39
Block: 288158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 936491 RingCT/type: yes/0
Extra: 01bc6a0d284c45336fe1e3b451a2476cdd9b7cfd6865de4deb4f22fbafd00dc7a5021100000013bffe00bb000000000000000000

1 output(s) for total of 68.110400435000 dcy

stealth address amount amount idx
00: 2bc9164a75a2b2b2b3d7a2c1630f2dd844b6ec424706046ee18e7adbd027807b 68.110400435000 603757 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": 288168, "vin": [ { "gen": { "height": 288158 } } ], "vout": [ { "amount": 68110400435, "target": { "key": "2bc9164a75a2b2b2b3d7a2c1630f2dd844b6ec424706046ee18e7adbd027807b" } } ], "extra": [ 1, 188, 106, 13, 40, 76, 69, 51, 111, 225, 227, 180, 81, 162, 71, 108, 221, 155, 124, 253, 104, 101, 222, 77, 235, 79, 34, 251, 175, 208, 13, 199, 165, 2, 17, 0, 0, 0, 19, 191, 254, 0, 187, 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