Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7e9da06a807ceb146943c03f6c81bbea188db21ee624046b29d356894fc8811

Tx prefix hash: c567e317c4b6a1d093e12d0f0956547dff2813f2c05a08b6b42e2cdf9f02015d
Tx public key: b63fe9ee5077a5bcdf8b64e45cacbadeafdc108078bd3763496927d29b54f457
Timestamp: 1581823648 Timestamp [UCT]: 2020-02-16 03:27:28 Age [y:d:h:m:s]: 04:324:07:19:47
Block: 65934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124044 RingCT/type: yes/0
Extra: 01b63fe9ee5077a5bcdf8b64e45cacbadeafdc108078bd3763496927d29b54f457021100000003c71d3ff9000000000000000000

1 output(s) for total of 371.136866878000 dcy

stealth address amount amount idx
00: dde7d3d6fa1018483120f528a89f8f5cba6726ad104e6b3b703be53cd000276b 371.136866878000 121561 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": 65944, "vin": [ { "gen": { "height": 65934 } } ], "vout": [ { "amount": 371136866878, "target": { "key": "dde7d3d6fa1018483120f528a89f8f5cba6726ad104e6b3b703be53cd000276b" } } ], "extra": [ 1, 182, 63, 233, 238, 80, 119, 165, 188, 223, 139, 100, 228, 92, 172, 186, 222, 175, 220, 16, 128, 120, 189, 55, 99, 73, 105, 39, 210, 155, 84, 244, 87, 2, 17, 0, 0, 0, 3, 199, 29, 63, 249, 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