Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 151bc21f518e73c14688281db2aa3b9bd3cbc6da5eb59e3a00f5143a519255f9

Tx prefix hash: 7391771ef2964a68ff044c09a0ff4ea60874b4d919ca4fc2573dfd7e15ed13c4
Tx public key: d3f89e8817eb88723474a9bb76d0ca45aa80c377c88d586f20ef03d5846f65ab
Timestamp: 1649911251 Timestamp [UCT]: 2022-04-14 04:40:51 Age [y:d:h:m:s]: 02:255:21:40:03
Block: 479788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 702787 RingCT/type: yes/0
Extra: 01d3f89e8817eb88723474a9bb76d0ca45aa80c377c88d586f20ef03d5846f65ab02110000000133af99f4000000000000000000

1 output(s) for total of 15.785684613000 dcy

stealth address amount amount idx
00: 8076f0ae9df976eddc8e0beef6a0ecef4f120e0d064c72b8eb95bf34e8bf9b34 15.785684613000 900751 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": 479798, "vin": [ { "gen": { "height": 479788 } } ], "vout": [ { "amount": 15785684613, "target": { "key": "8076f0ae9df976eddc8e0beef6a0ecef4f120e0d064c72b8eb95bf34e8bf9b34" } } ], "extra": [ 1, 211, 248, 158, 136, 23, 235, 136, 114, 52, 116, 169, 187, 118, 208, 202, 69, 170, 128, 195, 119, 200, 141, 88, 111, 32, 239, 3, 213, 132, 111, 101, 171, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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