Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cf7c603674c48c0416c232f1c3778e3ad0265c6a7679a054120c7d63810c758

Tx prefix hash: 9229899e97762e1feac899c690573ac9b472067a15719099905aadf2ecaddc0d
Tx public key: 4408069a8465bb1e687b0fa2898c9b0d7ae45a7cb026285bfc2fb05daa3f751c
Timestamp: 1711145239 Timestamp [UCT]: 2024-03-22 22:07:19 Age [y:d:h:m:s]: 00:361:23:44:49
Block: 984169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258815 RingCT/type: yes/0
Extra: 014408069a8465bb1e687b0fa2898c9b0d7ae45a7cb026285bfc2fb05daa3f751c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 432147513a1ac25f3ba8788aedf1ccc16bf346bd456a45e0d18e11200b121dce 0.600000000000 1444334 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": 984179, "vin": [ { "gen": { "height": 984169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "432147513a1ac25f3ba8788aedf1ccc16bf346bd456a45e0d18e11200b121dce" } } ], "extra": [ 1, 68, 8, 6, 154, 132, 101, 187, 30, 104, 123, 15, 162, 137, 140, 155, 13, 122, 228, 90, 124, 176, 38, 40, 91, 252, 47, 176, 93, 170, 63, 117, 28, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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