Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f928655a424dc48bf9fa3b4df4f6e432159e700dde80eab13cff62d2d1385ee

Tx prefix hash: f43adb787f5b1aa9f7ae6609cf087660982baef1156ac17b9a03413115c6d679
Tx public key: 8a3602906974de2577b658fdced1d6d3908fc97aef6d21e5a4aa056e2b1c708a
Timestamp: 1735585171 Timestamp [UCT]: 2024-12-30 18:59:31 Age [y:d:h:m:s]: 00:325:20:01:24
Block: 1186632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230388 RingCT/type: yes/0
Extra: 018a3602906974de2577b658fdced1d6d3908fc97aef6d21e5a4aa056e2b1c708a021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a39ddb3c5ec77b1f3c8e3e146a12a141ebb86467e061ed6560d923427dd9b945 0.600000000000 1673115 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": 1186642, "vin": [ { "gen": { "height": 1186632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a39ddb3c5ec77b1f3c8e3e146a12a141ebb86467e061ed6560d923427dd9b945" } } ], "extra": [ 1, 138, 54, 2, 144, 105, 116, 222, 37, 119, 182, 88, 253, 206, 209, 214, 211, 144, 143, 201, 122, 239, 109, 33, 229, 164, 170, 5, 110, 43, 28, 112, 138, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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