Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64cb7be63b76a0afbfcca8d7b9bd5573ccdccca966f7c5765e5ddb65976d308c

Tx prefix hash: 2a7421aef680e18a5d0e2013643cda48f11a424e00ed06d61ac6d57a2ecfcf24
Tx public key: 861dc59c139f8c4d518d7f020cedd0a7797cf98de0616fc1b67905e13d5a0778
Timestamp: 1684606263 Timestamp [UCT]: 2023-05-20 18:11:03 Age [y:d:h:m:s]: 01:324:06:20:33
Block: 764379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492958 RingCT/type: yes/0
Extra: 01861dc59c139f8c4d518d7f020cedd0a7797cf98de0616fc1b67905e13d5a077802110000000333af99f4000000000000000000

1 output(s) for total of 1.800094257000 dcy

stealth address amount amount idx
00: 4f9c1d0968395f16cde2105ed4c230ce1abe0a58566dd7034936c30ca7cf4e20 1.800094257000 1213296 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": 764389, "vin": [ { "gen": { "height": 764379 } } ], "vout": [ { "amount": 1800094257, "target": { "key": "4f9c1d0968395f16cde2105ed4c230ce1abe0a58566dd7034936c30ca7cf4e20" } } ], "extra": [ 1, 134, 29, 197, 156, 19, 159, 140, 77, 81, 141, 127, 2, 12, 237, 208, 167, 121, 124, 249, 141, 224, 97, 111, 193, 182, 121, 5, 225, 61, 90, 7, 120, 2, 17, 0, 0, 0, 3, 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