Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d560c6afdce8a5d954ede9d443e424f02d093521ec3321a101659699604d8c0

Tx prefix hash: 746c17d72118e1c452c6720df07db6134e12c5df3ed84c824e3b1b6f9b068391
Tx public key: 135490d9e8522435fea76161ad0d6f18aa30da645fcdfeca0eead57cf8bfc741
Timestamp: 1696884704 Timestamp [UCT]: 2023-10-09 20:51:44 Age [y:d:h:m:s]: 01:232:17:07:50
Block: 866124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427408 RingCT/type: yes/0
Extra: 01135490d9e8522435fea76161ad0d6f18aa30da645fcdfeca0eead57cf8bfc741021100000001e08532b6000000000000000000

1 output(s) for total of 0.828269512000 dcy

stealth address amount amount idx
00: 5d88798c7bb88fb77a019cd98c0a65cd8c1561ce49c872bb12f2a9ef3ca97943 0.828269512000 1320696 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": 866134, "vin": [ { "gen": { "height": 866124 } } ], "vout": [ { "amount": 828269512, "target": { "key": "5d88798c7bb88fb77a019cd98c0a65cd8c1561ce49c872bb12f2a9ef3ca97943" } } ], "extra": [ 1, 19, 84, 144, 217, 232, 82, 36, 53, 254, 167, 97, 97, 173, 13, 111, 24, 170, 48, 218, 100, 95, 205, 254, 202, 14, 234, 213, 124, 248, 191, 199, 65, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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