Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0401ecd1c32318f921bd5d481ccae344d352f13c7599231748d540cb0d4743d

Tx prefix hash: e713de2fbbcded4dbfa3552e71b52eddc6f80de0b463418c806888cbd0df0bd2
Tx public key: dc24ccf0dc3bc0c7fa13d2672855382dd60355d415eaa646891fc581fdc3a3c5
Timestamp: 1577816193 Timestamp [UCT]: 2019-12-31 18:16:33 Age [y:d:h:m:s]: 04:325:06:38:51
Block: 35931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1121554 RingCT/type: yes/0
Extra: 01dc24ccf0dc3bc0c7fa13d2672855382dd60355d415eaa646891fc581fdc3a3c50211000000324ac5aa02000000000000000000

1 output(s) for total of 466.601934404000 dcy

stealth address amount amount idx
00: e0cab576cc2b6552c33b2e560e99aa6e6b59dabee5f2b5e09f08a4d0658eb1c6 466.601934404000 60701 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": 35941, "vin": [ { "gen": { "height": 35931 } } ], "vout": [ { "amount": 466601934404, "target": { "key": "e0cab576cc2b6552c33b2e560e99aa6e6b59dabee5f2b5e09f08a4d0658eb1c6" } } ], "extra": [ 1, 220, 36, 204, 240, 220, 59, 192, 199, 250, 19, 210, 103, 40, 85, 56, 45, 214, 3, 85, 212, 21, 234, 166, 70, 137, 31, 197, 129, 253, 195, 163, 197, 2, 17, 0, 0, 0, 50, 74, 197, 170, 2, 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