Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fe6f24e12677959b741bc544f382a646872737cb7c0d3fad7249aaa36799cfd

Tx prefix hash: d0f3fd24ab0551c789da11b44a55a1f9c140ade9b36b81bc70c2ee424c2a4d72
Tx public key: 384ef593999ea4f8ac2b8a2420c76531a457edefe362a7757b9962963c7e0ee7
Timestamp: 1696863321 Timestamp [UCT]: 2023-10-09 14:55:21 Age [y:d:h:m:s]: 01:176:07:29:54
Block: 865951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387029 RingCT/type: yes/0
Extra: 01384ef593999ea4f8ac2b8a2420c76531a457edefe362a7757b9962963c7e0ee70211000000064b8f5122000000000000000000

1 output(s) for total of 0.829363459000 dcy

stealth address amount amount idx
00: 061ad5a63c18ed96bfae24eb9e77e37342bdd0f284241b359b945e04028ce24f 0.829363459000 1320517 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": 865961, "vin": [ { "gen": { "height": 865951 } } ], "vout": [ { "amount": 829363459, "target": { "key": "061ad5a63c18ed96bfae24eb9e77e37342bdd0f284241b359b945e04028ce24f" } } ], "extra": [ 1, 56, 78, 245, 147, 153, 158, 164, 248, 172, 43, 138, 36, 32, 199, 101, 49, 164, 87, 237, 239, 227, 98, 167, 117, 123, 153, 98, 150, 60, 126, 14, 231, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 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