Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8f783db4bdaa340e7b845732489fbec260abd6625a97637b11ac9ae644480b8

Tx prefix hash: 933e314d8285477fdd2a78d2ae821959b888bc4cfb4c46ac60d63ad007541703
Tx public key: 9d947ab8c4eb83629731a3aa6c3d10d62b5437ae5864f37ca0b7a3b478c827ab
Timestamp: 1709517147 Timestamp [UCT]: 2024-03-04 01:52:27 Age [y:d:h:m:s]: 01:105:23:24:43
Block: 970657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336662 RingCT/type: yes/0
Extra: 019d947ab8c4eb83629731a3aa6c3d10d62b5437ae5864f37ca0b7a3b478c827ab0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ce59142359589e5cd2c37c04aec9c3690e43c3e23fa1dbd3062b647a3b70cf0 0.600000000000 1430516 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": 970667, "vin": [ { "gen": { "height": 970657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ce59142359589e5cd2c37c04aec9c3690e43c3e23fa1dbd3062b647a3b70cf0" } } ], "extra": [ 1, 157, 148, 122, 184, 196, 235, 131, 98, 151, 49, 163, 170, 108, 61, 16, 214, 43, 84, 55, 174, 88, 100, 243, 124, 160, 183, 163, 180, 120, 200, 39, 171, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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