Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3035648baf35c8d3dfa16349a964e9f2664bbac1d992279caecd317d68d49fc5

Tx prefix hash: 6d4652301062f41d31bf64bf7858bf8ad95b8330f89dbd8ac4fbb46d5bf22a4a
Tx public key: 568c5395f717df2dc196d77ca7b3f3b2dfc64b5853b0fe19ea209ab4c708e986
Timestamp: 1576427550 Timestamp [UCT]: 2019-12-15 16:32:30 Age [y:d:h:m:s]: 05:018:23:12:13
Block: 27833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1160134 RingCT/type: yes/0
Extra: 01568c5395f717df2dc196d77ca7b3f3b2dfc64b5853b0fe19ea209ab4c708e986021100000007ad433a0b000000000000000000

1 output(s) for total of 496.339206929000 dcy

stealth address amount amount idx
00: d567f47c2b7e7f1c20ad3f256e2c46bd6a2b4f1f026a43e3741858ffccaa8dc5 496.339206929000 45893 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": 27843, "vin": [ { "gen": { "height": 27833 } } ], "vout": [ { "amount": 496339206929, "target": { "key": "d567f47c2b7e7f1c20ad3f256e2c46bd6a2b4f1f026a43e3741858ffccaa8dc5" } } ], "extra": [ 1, 86, 140, 83, 149, 247, 23, 223, 45, 193, 150, 215, 124, 167, 179, 243, 178, 223, 198, 75, 88, 83, 176, 254, 25, 234, 32, 154, 180, 199, 8, 233, 134, 2, 17, 0, 0, 0, 7, 173, 67, 58, 11, 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