Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7abe650fc0388e5ec1504fc101841e6626848df71060895606b1a9f94d6fea4e

Tx prefix hash: 92c0c5f493ffb0d355e0d93d996d7967b62d3d1740efb752ff5eb45370c14d9a
Tx public key: aa821c70ba4874e38c14e78465eb2b470bff11af7d19fecca896498ea402f4d0
Timestamp: 1736054310 Timestamp [UCT]: 2025-01-05 05:18:30 Age [y:d:h:m:s]: 00:093:23:18:12
Block: 1190528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66930 RingCT/type: yes/0
Extra: 01aa821c70ba4874e38c14e78465eb2b470bff11af7d19fecca896498ea402f4d0021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 218f41bf7ac5614d0f694d2b6bdb26fa858ba99e4e02404b104095c8848fd16e 0.600000000000 1677045 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": 1190538, "vin": [ { "gen": { "height": 1190528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "218f41bf7ac5614d0f694d2b6bdb26fa858ba99e4e02404b104095c8848fd16e" } } ], "extra": [ 1, 170, 130, 28, 112, 186, 72, 116, 227, 140, 20, 231, 132, 101, 235, 43, 71, 11, 255, 17, 175, 125, 25, 254, 204, 168, 150, 73, 142, 164, 2, 244, 208, 2, 17, 0, 0, 0, 4, 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