Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95743bacb92adb8e57a74aabd6f049d0c65cf79bae78f3c45b53b442d280333e

Tx prefix hash: 47e6905e49ef182e46c57550ab66d06217f614aa4136baa69a303d6088419f77
Tx public key: 27bab0fd921224e5dbcfe1bbfdc1a41a82e0b4fef2c215fd5f5d9fe31821fe22
Timestamp: 1577691637 Timestamp [UCT]: 2019-12-30 07:40:37 Age [y:d:h:m:s]: 05:034:12:32:40
Block: 34850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1174449 RingCT/type: yes/0
Extra: 0127bab0fd921224e5dbcfe1bbfdc1a41a82e0b4fef2c215fd5f5d9fe31821fe220211000000074943cd9f000000000000000000

1 output(s) for total of 470.466103224000 dcy

stealth address amount amount idx
00: 090a4c34fcee0ce1aa11d125948a9c682fb4efa85ef535481442dbe10e0c3fa4 470.466103224000 58723 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": 34860, "vin": [ { "gen": { "height": 34850 } } ], "vout": [ { "amount": 470466103224, "target": { "key": "090a4c34fcee0ce1aa11d125948a9c682fb4efa85ef535481442dbe10e0c3fa4" } } ], "extra": [ 1, 39, 186, 176, 253, 146, 18, 36, 229, 219, 207, 225, 187, 253, 193, 164, 26, 130, 224, 180, 254, 242, 194, 21, 253, 95, 93, 159, 227, 24, 33, 254, 34, 2, 17, 0, 0, 0, 7, 73, 67, 205, 159, 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