Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 807dbcc695de0d7ed4efe84da48b507defacab34d018f41e7888035f570d292f

Tx prefix hash: c245242992b76a43e5ac7b41afa0dd16e7f6df7601f84c50774624f342847b8d
Tx public key: 1c1ae7f9a004fb36dbf31b5eea1999f15d981cc093b65ff506ca8c57411ed9e9
Timestamp: 1582515403 Timestamp [UCT]: 2020-02-24 03:36:43 Age [y:d:h:m:s]: 05:079:16:53:24
Block: 71366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1210176 RingCT/type: yes/0
Extra: 011c1ae7f9a004fb36dbf31b5eea1999f15d981cc093b65ff506ca8c57411ed9e902110000000203d36d11000000000000000000

1 output(s) for total of 356.070191591000 dcy

stealth address amount amount idx
00: 4bfdfaed4c2a121bba14b2818f7addae6fe4abe38b832f8fa24bf3b785334243 356.070191591000 131825 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": 71376, "vin": [ { "gen": { "height": 71366 } } ], "vout": [ { "amount": 356070191591, "target": { "key": "4bfdfaed4c2a121bba14b2818f7addae6fe4abe38b832f8fa24bf3b785334243" } } ], "extra": [ 1, 28, 26, 231, 249, 160, 4, 251, 54, 219, 243, 27, 94, 234, 25, 153, 241, 93, 152, 28, 192, 147, 182, 95, 245, 6, 202, 140, 87, 65, 30, 217, 233, 2, 17, 0, 0, 0, 2, 3, 211, 109, 17, 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