Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 668bceab3a2a8e73d4e0a92174a373f160934f2783f91cb1b6ae38e5a0104ad2

Tx prefix hash: c77f4fe93c57e9e74a70d9ac0d061da2450df4a66d10fa27311fdbbbd614cec0
Tx public key: e6ad9943523bc9e94d5aed0585f893dc070e77c49b2ff08a4735c2e6c7d06230
Timestamp: 1734779265 Timestamp [UCT]: 2024-12-21 11:07:45 Age [y:d:h:m:s]: 00:014:18:46:25
Block: 1179994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10553 RingCT/type: yes/0
Extra: 01e6ad9943523bc9e94d5aed0585f893dc070e77c49b2ff08a4735c2e6c7d062300211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43d6b24a6cff5385d9961cab8b79e794b03ed882cb3975d2c400ab29d94f60f4 0.600000000000 1666397 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": 1180004, "vin": [ { "gen": { "height": 1179994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43d6b24a6cff5385d9961cab8b79e794b03ed882cb3975d2c400ab29d94f60f4" } } ], "extra": [ 1, 230, 173, 153, 67, 82, 59, 201, 233, 77, 90, 237, 5, 133, 248, 147, 220, 7, 14, 119, 196, 155, 47, 240, 138, 71, 53, 194, 230, 199, 208, 98, 48, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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