Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b138f6ff8e43cd120081d4972d1d4001649daf6c5ff06081cca9344657f578b6

Tx prefix hash: 1951b33a06de849e6e005023cfe997c8829dfd7f8a1e917a0d6f6c7b2b81d511
Tx public key: ca2c8cb20bac2328d5d60f6c6c14353c581db1f130785ac9895bdc4c2126d010
Timestamp: 1705985440 Timestamp [UCT]: 2024-01-23 04:50:40 Age [y:d:h:m:s]: 01:077:17:29:49
Block: 941333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316655 RingCT/type: yes/0
Extra: 01ca2c8cb20bac2328d5d60f6c6c14353c581db1f130785ac9895bdc4c2126d0100211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90803e13a9d27b42760315e90f9add6f1ad6b42c205f11d077e59d7c40d64313 0.600000000000 1399479 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": 941343, "vin": [ { "gen": { "height": 941333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90803e13a9d27b42760315e90f9add6f1ad6b42c205f11d077e59d7c40d64313" } } ], "extra": [ 1, 202, 44, 140, 178, 11, 172, 35, 40, 213, 214, 15, 108, 108, 20, 53, 60, 88, 29, 177, 241, 48, 120, 90, 201, 137, 91, 220, 76, 33, 38, 208, 16, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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