Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 331b32a497f547353b9d5e159c7f77161f5d97b759b8d717fd6a7ee0a158ff3e

Tx prefix hash: 003ed3acfd19692dedb2d8a8ca5d3d61e192bf2294af5d93715260d30010c6d8
Tx public key: f0e201452b6d476cc86bc5140b744c015d33305bd91e8ec2382587933f4437b8
Timestamp: 1578943844 Timestamp [UCT]: 2020-01-13 19:30:44 Age [y:d:h:m:s]: 05:296:12:00:45
Block: 44919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1359719 RingCT/type: yes/0
Extra: 01f0e201452b6d476cc86bc5140b744c015d33305bd91e8ec2382587933f4437b80211000000078a2ee0d9000000000000000000

1 output(s) for total of 435.677916044000 dcy

stealth address amount amount idx
00: b2b75ec4def3901c802d2f90a8ab8a8adaf9ab0739b4ee5440b17bc69a584940 435.677916044000 81898 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": 44929, "vin": [ { "gen": { "height": 44919 } } ], "vout": [ { "amount": 435677916044, "target": { "key": "b2b75ec4def3901c802d2f90a8ab8a8adaf9ab0739b4ee5440b17bc69a584940" } } ], "extra": [ 1, 240, 226, 1, 69, 43, 109, 71, 108, 200, 107, 197, 20, 11, 116, 76, 1, 93, 51, 48, 91, 217, 30, 142, 194, 56, 37, 135, 147, 63, 68, 55, 184, 2, 17, 0, 0, 0, 7, 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