Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b29d37186b227826719ca83618ed96119c4ea647dff8ef454cde32ec30ff9d23

Tx prefix hash: 4be252ff40968098ec361401b7eb8a062efd8ba79afbd3fc7cdffed18334c899
Tx public key: 1d572d6f1c1fe1945a049fd7b4052a4765f9e483ceff59a7aae9926ad138242c
Timestamp: 1700452865 Timestamp [UCT]: 2023-11-20 04:01:05 Age [y:d:h:m:s]: 01:118:07:19:27
Block: 895500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345742 RingCT/type: yes/0
Extra: 011d572d6f1c1fe1945a049fd7b4052a4765f9e483ceff59a7aae9926ad138242c021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.661967626000 dcy

stealth address amount amount idx
00: 06605f446e70f937199bd5eaf21538934ae3b49b1a527616ebf8542c8b4ea0c5 0.661967626000 1351737 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": 895510, "vin": [ { "gen": { "height": 895500 } } ], "vout": [ { "amount": 661967626, "target": { "key": "06605f446e70f937199bd5eaf21538934ae3b49b1a527616ebf8542c8b4ea0c5" } } ], "extra": [ 1, 29, 87, 45, 111, 28, 31, 225, 148, 90, 4, 159, 215, 180, 5, 42, 71, 101, 249, 228, 131, 206, 255, 89, 167, 170, 233, 146, 106, 209, 56, 36, 44, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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