Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7c2b72bb33a20a81a95f0f7ec4c555f5692cf0f814ba34aca837731efd7367e

Tx prefix hash: f72b243fb6d93592a4a97f0852d10c4912067f7b85fc48ed18819a5e3b5eb0f0
Tx public key: 0c45ab33d7427fd55c22b4821d9968b2ac3acdb2aae8f50541f8e15f39ef1223
Timestamp: 1581235221 Timestamp [UCT]: 2020-02-09 08:00:21 Age [y:d:h:m:s]: 05:270:20:52:45
Block: 61113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1344156 RingCT/type: yes/0
Extra: 010c45ab33d7427fd55c22b4821d9968b2ac3acdb2aae8f50541f8e15f39ef12230211000000028a2ee0d9000000000000000000

1 output(s) for total of 385.085756933000 dcy

stealth address amount amount idx
00: 28aeab8e75389ddcf7a3ad34bfe8aa3585c51f6ad2847dd01dd1f1fd310b8a6d 385.085756933000 112626 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": 61123, "vin": [ { "gen": { "height": 61113 } } ], "vout": [ { "amount": 385085756933, "target": { "key": "28aeab8e75389ddcf7a3ad34bfe8aa3585c51f6ad2847dd01dd1f1fd310b8a6d" } } ], "extra": [ 1, 12, 69, 171, 51, 215, 66, 127, 213, 92, 34, 180, 130, 29, 153, 104, 178, 172, 58, 205, 178, 170, 232, 245, 5, 65, 248, 225, 95, 57, 239, 18, 35, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 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