Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0315399afcb549dda7c95b2b2d9382a4da570ceab06e5bd915c33d76723a546

Tx prefix hash: 831c0cdaadfcd71a03bdf24c9aa2d7cef8ab6833fc6ae6f6e3f311385e944af6
Tx public key: b448527de87bf3fd71250b7433e4d45090c137ee7fcbe4629629a6b6e8a47bba
Timestamp: 1738581916 Timestamp [UCT]: 2025-02-03 11:25:16 Age [y:d:h:m:s]: 00:289:20:36:13
Block: 1211169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204936 RingCT/type: yes/0
Extra: 01b448527de87bf3fd71250b7433e4d45090c137ee7fcbe4629629a6b6e8a47bba0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0db087d0f7171a15210c4830cb787a33400c09c4c3d51d7d3aeec77a9f09c986 0.600000000000 1697928 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": 1211179, "vin": [ { "gen": { "height": 1211169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0db087d0f7171a15210c4830cb787a33400c09c4c3d51d7d3aeec77a9f09c986" } } ], "extra": [ 1, 180, 72, 82, 125, 232, 123, 243, 253, 113, 37, 11, 116, 51, 228, 212, 80, 144, 193, 55, 238, 127, 203, 228, 98, 150, 41, 166, 182, 232, 164, 123, 186, 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