Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 487d90961a7316fa90f96e3d61f9b5050dfe50cc411c9f6404c7dd8c378b2e45

Tx prefix hash: 0022b2fa693db65f4389d1229ff97f2a410055c9910cda3080ff9e108578e8a1
Tx public key: 35f9c3a72c678bad27424fbbde41b1e0b95f4ced3df64f3e3b00910438062ac2
Timestamp: 1709039101 Timestamp [UCT]: 2024-02-27 13:05:01 Age [y:d:h:m:s]: 01:087:11:07:07
Block: 966692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323555 RingCT/type: yes/0
Extra: 0135f9c3a72c678bad27424fbbde41b1e0b95f4ced3df64f3e3b00910438062ac20211000000010546d7d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66c5aae4716948b4eb71816487a01f5601081ebc78d692d293a998468a484cd8 0.600000000000 1426463 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": 966702, "vin": [ { "gen": { "height": 966692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66c5aae4716948b4eb71816487a01f5601081ebc78d692d293a998468a484cd8" } } ], "extra": [ 1, 53, 249, 195, 167, 44, 103, 139, 173, 39, 66, 79, 187, 222, 65, 177, 224, 185, 95, 76, 237, 61, 246, 79, 62, 59, 0, 145, 4, 56, 6, 42, 194, 2, 17, 0, 0, 0, 1, 5, 70, 215, 208, 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