Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc3a3e7a2ce110f61b4ab9b8c57b924e02c7250312967251a90a425ecc04d407

Tx prefix hash: 6ddaec9318867660a26225882768aa8b3762a728723f832a61d50450de81cd8a
Tx public key: c10807b3f5150aa447d8979fe24f25edcdc4f118e47d01b83df4385b6f258579
Timestamp: 1703112773 Timestamp [UCT]: 2023-12-20 22:52:53 Age [y:d:h:m:s]: 01:111:01:15:03
Block: 917579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340463 RingCT/type: yes/0
Extra: 01c10807b3f5150aa447d8979fe24f25edcdc4f118e47d01b83df4385b6f258579021100000004c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57f5b1d58d54b518296f9777d1a6f99f9b39411b8e75da0b4c2a7b706ce5833f 0.600000000000 1375161 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": 917589, "vin": [ { "gen": { "height": 917579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57f5b1d58d54b518296f9777d1a6f99f9b39411b8e75da0b4c2a7b706ce5833f" } } ], "extra": [ 1, 193, 8, 7, 179, 245, 21, 10, 164, 71, 216, 151, 159, 226, 79, 37, 237, 205, 196, 241, 24, 228, 125, 1, 184, 61, 244, 56, 91, 111, 37, 133, 121, 2, 17, 0, 0, 0, 4, 197, 69, 41, 96, 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