Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f1b2f53328f3d7397a3d885131af6cdb480f74e68792203dcef5decd9080a2b

Tx prefix hash: 6de981e071f8975c082609c9ad04065addd09870e3482640f02033f1da76657b
Tx public key: 99d45abfcd4f737e56b43e11081f0d1b8be69081e1f8a2ef79a7bd1d3106cdda
Timestamp: 1730417443 Timestamp [UCT]: 2024-10-31 23:30:43 Age [y:d:h:m:s]: 00:082:05:08:21
Block: 1143833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58783 RingCT/type: yes/0
Extra: 0199d45abfcd4f737e56b43e11081f0d1b8be69081e1f8a2ef79a7bd1d3106cdda021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efec1e22e8ac5bc7bf627649a2c23995694e62adc4d6c8841b3cb58f5cfbe933 0.600000000000 1627842 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": 1143843, "vin": [ { "gen": { "height": 1143833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efec1e22e8ac5bc7bf627649a2c23995694e62adc4d6c8841b3cb58f5cfbe933" } } ], "extra": [ 1, 153, 212, 90, 191, 205, 79, 115, 126, 86, 180, 62, 17, 8, 31, 13, 27, 139, 230, 144, 129, 225, 248, 162, 239, 121, 167, 189, 29, 49, 6, 205, 218, 2, 17, 0, 0, 0, 1, 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