Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0c4b70699d3dda6012a02cd475f1905b31efaaa78618b067901ce7e37ebf2a2

Tx prefix hash: 9a129fc299ffca8f51b3198d2b74670ffe985d212a23a3ae020a19b53823b700
Tx public key: f0174ce003a701be7213a2e5fcbdd0b6c95c630b9b6b789ca6d39257c0dd2ba9
Timestamp: 1581517350 Timestamp [UCT]: 2020-02-12 14:22:30 Age [y:d:h:m:s]: 04:324:12:26:13
Block: 63587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123991 RingCT/type: yes/0
Extra: 01f0174ce003a701be7213a2e5fcbdd0b6c95c630b9b6b789ca6d39257c0dd2ba90211000000017adf42d3000000000000000000

1 output(s) for total of 377.842395392000 dcy

stealth address amount amount idx
00: f678bff634bd459321e0f96ba7afe6beeddc8b5dabc2367c8d359203d02e29e9 377.842395392000 117180 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": 63597, "vin": [ { "gen": { "height": 63587 } } ], "vout": [ { "amount": 377842395392, "target": { "key": "f678bff634bd459321e0f96ba7afe6beeddc8b5dabc2367c8d359203d02e29e9" } } ], "extra": [ 1, 240, 23, 76, 224, 3, 167, 1, 190, 114, 19, 162, 229, 252, 189, 208, 182, 201, 92, 99, 11, 155, 107, 120, 156, 166, 211, 146, 87, 192, 221, 43, 169, 2, 17, 0, 0, 0, 1, 122, 223, 66, 211, 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