Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83702fe56033b781359f45d6b966b08aa1f3db1ae73347192e74e9b60a37a7e9

Tx prefix hash: 480b47b8cf9e9d43a8e03ad196533c0b233a61dda0ece59abbb8b58df855f2d4
Tx public key: 995dd08df4a2faf3c98df19a2dba8646beb9375ae2060b6bf6e4cd9226bf6fc7
Timestamp: 1706865356 Timestamp [UCT]: 2024-02-02 09:15:56 Age [y:d:h:m:s]: 01:093:08:38:19
Block: 948655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327811 RingCT/type: yes/0
Extra: 01995dd08df4a2faf3c98df19a2dba8646beb9375ae2060b6bf6e4cd9226bf6fc702110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db9659f362c2e53967cafdd0c42696cb53ce390d5089f1b1aca517467f81b567 0.600000000000 1407107 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": 948665, "vin": [ { "gen": { "height": 948655 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db9659f362c2e53967cafdd0c42696cb53ce390d5089f1b1aca517467f81b567" } } ], "extra": [ 1, 153, 93, 208, 141, 244, 162, 250, 243, 201, 141, 241, 154, 45, 186, 134, 70, 190, 185, 55, 90, 226, 6, 11, 107, 246, 228, 205, 146, 38, 191, 111, 199, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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