Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88a02c523b50e146caf0ac7a4cd03ab66807ccd75641083f5f42b9a339799281

Tx prefix hash: 7cbc796444e7d70b46d71177c5d2bc843de242cb662e49cc7a85c2ce0584060d
Tx public key: 9eadb4edddd4acf3530960c338d447b9f906414eb04a7b658675012d6d6fccc7
Timestamp: 1703760266 Timestamp [UCT]: 2023-12-28 10:44:26 Age [y:d:h:m:s]: 01:341:16:03:05
Block: 922917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503055 RingCT/type: yes/0
Extra: 019eadb4edddd4acf3530960c338d447b9f906414eb04a7b658675012d6d6fccc702110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 415371b0c65e2c2f1e6fc51b9d7f72415257bfcf557c6ae323ae4e68d05610d0 0.600000000000 1380623 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": 922927, "vin": [ { "gen": { "height": 922917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "415371b0c65e2c2f1e6fc51b9d7f72415257bfcf557c6ae323ae4e68d05610d0" } } ], "extra": [ 1, 158, 173, 180, 237, 221, 212, 172, 243, 83, 9, 96, 195, 56, 212, 71, 185, 249, 6, 65, 78, 176, 74, 123, 101, 134, 117, 1, 45, 109, 111, 204, 199, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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