Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a145250b81cb97d08d7d914a4d782167fb8f0838f6502458974601245c466183

Tx prefix hash: cb8f20bbff4c2e9e87f67e66e4f921016f8f41fc415e253851f0ad6ad04b165a
Tx public key: 18c8a9f610df2d7b48f4286a1a86e94f4068aae714a094330f9265a299ae1abf
Timestamp: 1708520341 Timestamp [UCT]: 2024-02-21 12:59:01 Age [y:d:h:m:s]: 01:056:20:10:49
Block: 962387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301654 RingCT/type: yes/0
Extra: 0118c8a9f610df2d7b48f4286a1a86e94f4068aae714a094330f9265a299ae1abf02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90e4e2471b8cc59e40561b751faccce5a5dc29f8c96a2c839939c380f3eb4927 0.600000000000 1422022 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": 962397, "vin": [ { "gen": { "height": 962387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90e4e2471b8cc59e40561b751faccce5a5dc29f8c96a2c839939c380f3eb4927" } } ], "extra": [ 1, 24, 200, 169, 246, 16, 223, 45, 123, 72, 244, 40, 106, 26, 134, 233, 79, 64, 104, 170, 231, 20, 160, 148, 51, 15, 146, 101, 162, 153, 174, 26, 191, 2, 17, 0, 0, 0, 3, 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