Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80a805a8481197804fc42622cbc03d3f0916b6f0456c350f5e705a5b230e0064

Tx prefix hash: bf2aef00537d60fd18c1a0dcf333bac53a17432af0fd3678b5f5bbbc69e1abe7
Tx public key: 91d9ca12d6105b04fac3e03d9df4e1772bff4361239e7edc9a0bf8b8f2c1f3f4
Timestamp: 1695981658 Timestamp [UCT]: 2023-09-29 10:00:58 Age [y:d:h:m:s]: 01:243:06:24:19
Block: 858638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434962 RingCT/type: yes/0
Extra: 0191d9ca12d6105b04fac3e03d9df4e1772bff4361239e7edc9a0bf8b8f2c1f3f4021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.876952181000 dcy

stealth address amount amount idx
00: 550f38785a62cf9d0d9eb458dc9775a57fcd36f236cca9ba738d93159c079fd9 0.876952181000 1312822 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": 858648, "vin": [ { "gen": { "height": 858638 } } ], "vout": [ { "amount": 876952181, "target": { "key": "550f38785a62cf9d0d9eb458dc9775a57fcd36f236cca9ba738d93159c079fd9" } } ], "extra": [ 1, 145, 217, 202, 18, 214, 16, 91, 4, 250, 195, 224, 61, 157, 244, 225, 119, 43, 255, 67, 97, 35, 158, 126, 220, 154, 11, 248, 184, 242, 193, 243, 244, 2, 17, 0, 0, 0, 3, 230, 210, 127, 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