Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2185498e6af672adf70c764b47019a49ed43562b4a05fc64f6c744af5913600

Tx prefix hash: 05ffe63d1b503d7119d485d01d2dc3100c7f0c147bef8ce8af899758b432697e
Tx public key: b58f75f3fc9f09b64f8d7829e1704dc398cd0a8487628180e767041a7bd44d7e
Timestamp: 1688795887 Timestamp [UCT]: 2023-07-08 05:58:07 Age [y:d:h:m:s]: 01:206:19:07:29
Block: 799121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408905 RingCT/type: yes/0
Extra: 01b58f75f3fc9f09b64f8d7829e1704dc398cd0a8487628180e767041a7bd44d7e021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.380958181000 dcy

stealth address amount amount idx
00: 27017522b8c03192ac174601553d9a6f5aac1a0202ccbb15b49cbe8904bde7df 1.380958181000 1250102 of 0

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": 799131, "vin": [ { "gen": { "height": 799121 } } ], "vout": [ { "amount": 1380958181, "target": { "key": "27017522b8c03192ac174601553d9a6f5aac1a0202ccbb15b49cbe8904bde7df" } } ], "extra": [ 1, 181, 143, 117, 243, 252, 159, 9, 182, 79, 141, 120, 41, 225, 112, 77, 195, 152, 205, 10, 132, 135, 98, 129, 128, 231, 103, 4, 26, 123, 212, 77, 126, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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