Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5653c9d19509e54046fa4b0588fb3ff4f5711e15a5c0bc4c879269f904dc7716

Tx prefix hash: c32cbd3acb7ef626e1cb9abb99c90a3066112ed2c81c8a6703c3973dd5a9d60c
Tx public key: 28b1a0e6d21cc85252b348f41974d4daf02778253abd02f93053270ae11747dd
Timestamp: 1700990274 Timestamp [UCT]: 2023-11-26 09:17:54 Age [y:d:h:m:s]: 01:202:03:30:07
Block: 899950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405591 RingCT/type: yes/0
Extra: 0128b1a0e6d21cc85252b348f41974d4daf02778253abd02f93053270ae11747dd021100000004faf35c9c000000000000000000

1 output(s) for total of 0.639870438000 dcy

stealth address amount amount idx
00: 159f8e44c10ad1b325ec72ef88fe8154c4d0c419fd1b2c240b6c2bfae5fdbef1 0.639870438000 1356421 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": 899960, "vin": [ { "gen": { "height": 899950 } } ], "vout": [ { "amount": 639870438, "target": { "key": "159f8e44c10ad1b325ec72ef88fe8154c4d0c419fd1b2c240b6c2bfae5fdbef1" } } ], "extra": [ 1, 40, 177, 160, 230, 210, 28, 200, 82, 82, 179, 72, 244, 25, 116, 212, 218, 240, 39, 120, 37, 58, 189, 2, 249, 48, 83, 39, 10, 225, 23, 71, 221, 2, 17, 0, 0, 0, 4, 250, 243, 92, 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