Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e61f53bec3adffe954376561206bc2d1c9572e7e2ca6619b72a9378792cbf69

Tx prefix hash: fc03509d549727adad03921ced7389b42a0fe39652789ea438272b1bd093a49c
Tx public key: 3f87615288aa10b5e1b843616e7f2b8095cf419af4b4bb6aa6d0466954a95e5d
Timestamp: 1735328277 Timestamp [UCT]: 2024-12-27 19:37:57 Age [y:d:h:m:s]: 00:310:19:35:26
Block: 1184503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219644 RingCT/type: yes/0
Extra: 013f87615288aa10b5e1b843616e7f2b8095cf419af4b4bb6aa6d0466954a95e5d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1da55166e9175139d50a41c3ed7d9f35623f8d13bd6934c636db6cb462a0b9d 0.600000000000 1670960 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": 1184513, "vin": [ { "gen": { "height": 1184503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1da55166e9175139d50a41c3ed7d9f35623f8d13bd6934c636db6cb462a0b9d" } } ], "extra": [ 1, 63, 135, 97, 82, 136, 170, 16, 181, 225, 184, 67, 97, 110, 127, 43, 128, 149, 207, 65, 154, 244, 180, 187, 106, 166, 208, 70, 105, 84, 169, 94, 93, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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