Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a0256ea09ef4817d8dad9268cf46f61d72e7dbb70c7170195ea6bafee2f365d

Tx prefix hash: d77ec3efdc87fdf9af1599b82bac96afc00616cca72bf5fa26bc919ac5cf1f0a
Tx public key: 4fb27338cb409a9492d08056f766f2bbf713315cf4f53449acd3d1ea0b1c68b7
Timestamp: 1722621075 Timestamp [UCT]: 2024-08-02 17:51:15 Age [y:d:h:m:s]: 00:083:15:24:34
Block: 1079284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59873 RingCT/type: yes/0
Extra: 014fb27338cb409a9492d08056f766f2bbf713315cf4f53449acd3d1ea0b1c68b7021100000001ef5a8513000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef547f661d77ca81fe41608b5bfadbaf929de97e75eb946ab692c816c80e6439 0.600000000000 1552171 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": 1079294, "vin": [ { "gen": { "height": 1079284 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef547f661d77ca81fe41608b5bfadbaf929de97e75eb946ab692c816c80e6439" } } ], "extra": [ 1, 79, 178, 115, 56, 203, 64, 154, 148, 146, 208, 128, 86, 247, 102, 242, 187, 247, 19, 49, 92, 244, 245, 52, 73, 172, 211, 209, 234, 11, 28, 104, 183, 2, 17, 0, 0, 0, 1, 239, 90, 133, 19, 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