Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 553696868c55f131b1d562cb34d8c46d8c5374e185ef09a8c3070cad96a5b1b7

Tx prefix hash: d7b1f364be23d8b8a77b239574b02b7c172cb1666b53de0d2df86078c65a7b86
Tx public key: 35011ea5f9a01b33e17c6460f082c89a2aaf5b814ab1b92d3bbeb2d581a80a84
Timestamp: 1706363979 Timestamp [UCT]: 2024-01-27 13:59:39 Age [y:d:h:m:s]: 01:029:02:55:22
Block: 944481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281869 RingCT/type: yes/0
Extra: 0135011ea5f9a01b33e17c6460f082c89a2aaf5b814ab1b92d3bbeb2d581a80a8402110000000b81d71d55000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8fb065d3ca1f1d060a94ce4060dec6af3726cbbab1526c6c3db24c291027cf3d 0.600000000000 1402731 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": 944491, "vin": [ { "gen": { "height": 944481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fb065d3ca1f1d060a94ce4060dec6af3726cbbab1526c6c3db24c291027cf3d" } } ], "extra": [ 1, 53, 1, 30, 165, 249, 160, 27, 51, 225, 124, 100, 96, 240, 130, 200, 154, 42, 175, 91, 129, 74, 177, 185, 45, 59, 190, 178, 213, 129, 168, 10, 132, 2, 17, 0, 0, 0, 11, 129, 215, 29, 85, 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